-
-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[18.0][MIG] partner_identification_unique_by_category: Migration to 18.0 #1859
base: 18.0
Are you sure you want to change the base?
[18.0][MIG] partner_identification_unique_by_category: Migration to 18.0 #1859
Conversation
This module extends the module `partner_identification` to enforce having unique id numbers by categories. This option can be set by category. [UPD] Update partner_identification_unique_by_category.pot [UPD] README.rst [ADD] icon.png
Currently translated at 100.0% (9 of 9 strings) Translation: partner-contact-14.0/partner-contact-14.0-partner_identification_unique_by_category Translate-URL: https://translation.odoo-community.org/projects/partner-contact-14-0/partner-contact-14-0-partner_identification_unique_by_category/es/
f2d8ef6
to
d25bbde
Compare
|
||
from odoo.exceptions import ValidationError | ||
|
||
from odoo.addons.base.tests.common import SavepointCaseWithUserDemo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from odoo.addons.base.tests.common import SavepointCaseWithUserDemo | |
from odoo.tests.common import TransactionCase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @TDu , I have updated it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
d25bbde
to
d0bfab2
Compare
/caobot migration partner_identification_unique_by_category |
@chaule97 Thanks for this. Don't forget to add the depending PR in this one description to help review |
Sorry @TDu you are not allowed to mark the addon tobe migrated. To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons. If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the |
Depend on: